Credit card imaging for mobile payment and other applications

ABSTRACT

A mobile payment device includes a contactless payment module, a processing module, and a display module. The contactless payment module is coupled to execute a credit payment transaction. The processing module is coupled to detect the executing of the credit payment transaction and retrieve credit image data based on the detecting. The display module is coupled to process the credit image data into a displayed credit image.

CROSS-REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/091,343,entitled “Credit Card Imaging for Mobile Payment and OtherApplications,” (Attorney Docket No. P-14202US), filed Aug. 23, 2008,pending, which is hereby incorporated herein by reference in itsentirety and made part of the present U.S. Utility patent applicationfor all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to financial transactions and moreparticularly to credit card imaging.

2. Description of Related Art

Millions of credit card transactions are accurately processed every dayregardless of whether the purchaser is making a purchase using a creditcard or mobile payment device in his/her home town, in another part ofthe world, or via the internet. Each transaction has a two stageprocess: authorization and clearing & settlement. Authorization is theprocess of approving or declining the transaction at the commencement ofthe transaction and clearing & settlement is the process of making thepayment and accounting for the payment.

The authorization process begins when a point-of-sale terminal (physicalfor in-store purchases, virtual for internet purchases) obtains apurchaser's account information from a credit card or mobile paymentdevice information and further obtains a transaction amount. Theterminal transmits the account information and the transaction amount toan acquirer bank, which combines the account information and thetransaction amount into an authorization request. The acquirer banktransmits the authorization request to a proprietary transactionprocessing network (e.g., VisaNet®), which routes the authorizationrequest to an issuer bank (i.e., the bank that issued the credit card).Alternatively, the proprietary transaction processing network mayperform a stand-in review and authorization.

When the authorization request is sent to the issuer bank, the bank, ora designated third party, reviews the request and approves it or deniesit. The issuer bank transmits a response to the proprietary transactionprocessing network indicating its decision. The proprietary transactionprocessing network forwards the response to the acquirer bank, which inturn, forwards the response to the point-of-sale terminal.

The clearing & settlement process begins with clearing, which, in turn,begins when the point-of-sale terminal, or other merchant processingdevice, transmits sales draft information (e.g., account numbers andamounts) to the acquirer bank. The acquirer bank formats the sales draftinformation into a clearing message that it transmits to the proprietarytransaction processing network. The network transmits the clearingmessage to the issuer bank, which calculates settlement obligations ofthe issuer bank, processing fees, and the amount due the acquirer bank.Settlement begins when the issuer bank transmits funds to a designatedbank of the proprietary transaction processing network, which, afterprocessing, transfers the funds to the acquirer bank.

In an alternate credit card transaction processing system, theproprietary transaction network is owned by a single issuer bank. Thus,in contrast with the previously described system, the alternative systemincludes only one issue bank, not a large number of issuer banks, and,as such, the issuer bank's functions and the proprietary transactionnetwork functions previously discussed are merged. In this alternatesystem, the processing of the single issuer is less than the multipleissuer system but creates a processing bottleneck due to the singleissuer.

The use of mobile payment devices is gaining momentum in the marketplaceand consumers desire more features and ease of use. In addition, manytraditional credit card users would like similar additional featuresthat allow them to customize their use of credit cards.

Therefore, a need exists for a credit card imaging and applicationsthereof.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a financialtransaction network in accordance with the present invention;

FIG. 2 is a schematic block diagram of an embodiment of a mobile paymentdevice in accordance with the present invention;

FIG. 3 is a diagram of an example of a credit image displayed on amobile payment device in accordance with the present invention;

FIG. 4 is a logic diagram of an embodiment of a method for credit imagedata processing in accordance with the present invention;

FIG. 5 is a diagram of another example of a credit image in accordancewith the present invention;

FIG. 6 is a logic diagram of another embodiment of a method for creditimage data processing in accordance with the present invention;

FIG. 7 is a schematic block diagram of an embodiment of a contactlesspayment module in accordance with the present invention;

FIG. 8 is a schematic block diagram of an embodiment of a financialtransaction apparatus in accordance with the present invention;

FIG. 9 is a logic diagram of another embodiment of a method for creditimage data processing in accordance with the present invention;

FIG. 10 is a logic diagram of another embodiment of a method for creditimage data processing in accordance with the present invention; and

FIG. 11 is a logic diagram of another embodiment of a method for creditimage data processing in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a financialtransaction system 10 that includes a payment entity device 12, adatabase 14, a proprietary network 16, a plurality of proprietaryinterfaces 18-25, a proprietary gateway 26, a plurality of acquirerdevices 28-30, a plurality of issuer devices 32-34, a public network 36(e.g., the internet), a plurality of user devices 38-42, an plurality ofmerchant devices 44-52, and a plurality of mobile payment devices 54-56.The system 10 supports point of sale financial transactions, automaticpayment financial transactions, mobile payment device financialtransactions, user device public network based financial transactions,and/or any other type of credit account (e.g., credit card, pre-paidcard, corporate card, debit card, purchasing card, mobile paymentaccount, etc.) based financial transactions. The system 10 may alsosupport credit account communications (e.g., account balance inquires,usage offers, bonus programs, general credit account information, etc.)via the public network 36. The system 10 may further support proprietaryclient services (e.g., commercial accounts payable and/or accountsreceivable processing, financial reporting, etc.) for a client via itsassociated user device 38 and the proprietary gateway 26. Note that eachof connection lines n₁-n₆ includes a plurality of individual connectionlines for each device connected thereto, but are shown as a bundle forease of illustration.

As shown, each of the issuer devices 32-34 and acquirer devices 28-30 isconnected to the public network 36 and to the proprietary network 16 viaa proprietary interface 18-25 to support one or more of the variousfinancial transactions and credit account communications. For instance,a financial transaction may begin with a merchant device 44-52 (e.g., acomputer, server, point of sale device, web browser application, and/orany device that facilitates a credit account based transaction)obtaining a credit account information for a point of sale transaction,an internet transaction, a mobile payment transaction, etc. In addition,the merchant device 44-52 determines a corresponding transaction amountand transmits, via a connection line, the credit account information andthe transaction amount to an affiliated acquirer device 28-30.

The acquirer device 28-30 (e.g., a computer, server, etc. associatedwith a financial institution supporting credit account transactions of amerchant) generates an authorization request from the credit accountinformation and the transaction amount. The acquirer device 28-30transmits the authorization request to the payment entity device 12 viathe corresponding proprietary interface 18-20 and the proprietarynetwork 16. The payment entity device 12 accesses the associateddatabase 14 to identify the user associated with the credit accountinformation, an issuer, etc. Having identified the issuer, the paymententity device 12 transmits the authorization request to the appropriateissuer device 32-34 via the proprietary network 16 and the correspondingproprietary interface 22-24.

In an embodiment, the payment entity device 12, the database 14, and theproprietary network 16 may be operated and maintained by a single entityto facilitate seamless authorization and clearing & settlement. Forexample, Visa, Inc. may provide its VisaNet® as the proprietary network16 and have one or more computing devices (e.g., computers, servers,super computers, main frames, etc.) coupled to the proprietary network16 to function as the payment entity device 12, and may have one or moredatabases 14 coupled thereto. Further, the proprietary interfaces 18-25,which may be proprietary nodes, modems, bridges, etc., serve as secureconnection points to the proprietary network 16 to ensure that onlyauthorized devices (e.g., merchant device 44, issuer device 32-34,acquirer device 28-30) have access to the proprietary network 16.

The issuer device 32-34 (e.g., a computer, server, etc. andcorresponding financial transaction software associated with a financialinstitution that issues credit accounts to users) processes theauthorization request to determine whether to approve or deny therequest. The issuer device 32-34 transmits, via the associatedproprietary interface 22-24 and the proprietary network 16, an approvalor denial response to the payment entity device 12. The payment entitydevice 12 forwards the response to the acquirer device 28-30 via theproprietary network 16 and the corresponding proprietary interface18-20. The acquirer device 28-30 forwards the response to the merchantdevice 44-52 via the corresponding connection line. Note that the system10 also supports the clearing & settlement process.

The issuer devices 32-34, the acquirer devices 28-30, and/or the paymententity device 12 support credit account communications from users viathe user devices 38-42 and the public network 36, from merchants via themerchant devices 44-52 and the public network 36, etc. For example, auser device 38-42 may access a web site running on the payment entitydevice 12 (e.g., Visa, Inc.'s web site) to obtain information regardingvarious credit card offers supported by Visa, Inc. As another example, auser device 38-42 may access an issuer device 32-34 via the publicnetwork 36 to obtain current information regarding the user's accountwith the issuer, on-line bill payment, open a new account, etc.

In addition to accessing the payment entity device 12 via the publicnetwork 36, a user device 38 may have access to a proprietary gateway 26to access the payment entity device 12 via the proprietary network 16for a proprietary service (e.g., accounts payable, accounts receivable,financial reporting, elite class offers, etc.). Note that theproprietary gateway 26 may be a proprietary node, modem, bridge, etc.,that serves as a public connection point to the proprietary network 16.The proprietary gateway 26 functions to ensure that only authorizedentities (e.g., user device 38) have access to the proprietary network16.

As mentioned, the system 10 may support mobile payment transactionsinitiated by a mobile payment device 54-56. During the processing of acredit payment transaction initiated by the mobile payment device 54-56,the mobile payment device 54-56 may obtain a credit image data anddisplay it. The credit image data may be retrieved from memory, from afinancial institution server (e.g., the payment entity device 12, anissuer device 32-34, or an acquirer device 28-30), from a contactlesspayment module, from a corresponding user device 38-42. etc. Theprocessing, determining, generating, retrieving, and/or displaying ofcredit image data will be described in greater detail with reference toFIGS. 2-11.

FIG. 2 is a schematic block diagram of an embodiment of a mobile paymentdevice 54-56 that includes a contact less payment module 60, aprocessing module 62, a display module 64, and a bus 72. The displaymodule 64 may include a display 64 (e.g., an LCD (liquid crystaldisplay) display, a DLP (digital light projection) display, etc.) Theprocessing module 62 may be a single processing device or a plurality ofprocessing devices. Such a processing device may be a microprocessor,micro-controller, digital signal processor, microcomputer, centralprocessing unit, field programmable gate array, programmable logicdevice, state machine, logic circuitry, analog circuitry, digitalcircuitry, and/or any device that manipulates signals (analog and/ordigital) based on hard coding of the circuitry and/or operationalinstructions. The processing module 72 may have an associated memory 70and/or memory element, which may be a single memory device, a pluralityof memory devices, and/or embedded circuitry of the processing module.Such a memory device may be a read-only memory, random access memory,volatile memory, non-volatile memory, static memory, dynamic memory,flash memory, cache memory, and/or any device that stores digitalinformation. Note that when the processing module 62 implements one ormore of its functions via a state machine, analog circuitry, digitalcircuitry, and/or logic circuitry, the memory 70 and/or memory elementstoring the corresponding operational instructions may be embeddedwithin, or external to, the circuitry comprising the state machine,analog circuitry, digital circuitry, and/or logic circuitry. Furthernote that, the memory element stores, and the processing module 62executes, hard coded and/or operational instructions corresponding to atleast some of the steps and/or functions illustrated in FIGS. 2-11. Evenfurther note that the mobile payment device 54-56 may include a wirelesstransceiver 74 that provides cellular (e.g., voice) and data (e.g.,email, Internet access, etc.) telephone functionality for the mobilepayment device 54-56.

In operation, the contactless payment module 60 executes a creditpayment transaction. In general, when the contactless payment module 60is proximal to a point of sale terminal (e.g., for point of saletransactions), the contactless payment module 60 exchanges data (e.g.,account information, purchase price, etc.) with the point of saleterminal via radio frequency (RF) signals and/or electromagneticcoupling signals. For example, the contactless payment module may be asubscriber identity module (SIM) having a radio frequency identification(RFID) interface; a smart card with the RFID interface; a SIM having anear field communication (NFC) interface; and/or a smart card with theNFC interface. In addition to point of sale transactions, thecontactless payment module 60 may provide a remote-based transactions(e.g., internet or Short-Message-Service (SMS) based e-commercetransactions) payment method and/or money transfers between mobilepayment devices.

The processing module 60 is coupled to detect the executing of thecredit payment transaction. For example, the processing module 60detects the data exchange between the contactless payment module 60 andthe point of sale terminal and/or receives a signal from the contactlesspayment module 60 indicating initiation of the credit paymenttransaction. After detecting the executing, the processing module 62retrieves credit image data. The processing module 62 may retrieve thecredit image data from memory 70 and/or from the contactless paymentmodule 60. Alternatively, or in addition to, the processing module 62may retrieve the credit image data from a financial institution server(e.g., the payment entity device 12, an issuer device 32-34, or anacquirer device 28-30) via the wireless transceiver 74.

As an example of retrieving the credit image data at least partiallyfrom a financial institution server, the processing module 62 sends aretrieval message to the wireless transceiver 74 upon detecting theexecution of the credit payment transaction. The wireless transceiver 74converts the retrieval message into an RF signal that is transmitted toa cellular tower (not shown), which converts the RF signal into a datamessage that is forwarded to the financial institution server via thepublic network 36. The financial institution server processes theretrieval message to identify the user, the user's credit image data andany other pertinent data. The financial institution sends the user'scredit image data to the wireless transceiver 74 via the reverse pathfrom which it received the request message. The wireless transceiver 74recovers the credit image data from the received RF signal to producerecovered credit image data and provides the recovered credit image datato the processing module 62.

The processing module 62 coordinates the credit image data beingprovided to the display module 64. The graphics engine 68 (which may bea video graphics accelerator, a video decoder, an LCD driver, a DLPdriver, etc.) processes the credit image data to produce a displayedcredit image that is displayed via the display 66.

FIG. 3 is a diagram of an example of a credit image displayed on thedisplay 66 of a mobile payment device 54-56. In this example, the creditimage data a master image layer 80 (e.g., issuer's logo, credit cardlogo, cardholder's name, account number, expiration date, issuance date,etc.) and a design image layer 82 (e.g., a race car character). Thedesign layer 82 may be a custom design image layer (e.g., a digitalimage provided by the user of the mobile payment device 54-56) and/orone of a plurality of approved design image layers offered by thefinancial institution that operates the financial institution server.

FIG. 4 is a logic diagram of an embodiment of a method for credit imagedata processing that may be performed by the processing module 62. Themethod begins at step 90 where the processing module 62 detects theexecuting of the credit payment transaction by the contactless paymentmodule 60. In addition to detecting the executing of the paymenttransaction, the processing module 62 may detect a type of the creditpayment transaction (e.g., credit card, debit card, commercial purchasecard, pre-pay card, corporate card, etc.).

The method then proceeds to step 92 where the processing module 62retrieves the credit image data based on the detecting of the executingof the credit payment transaction. The processing module 62 may retrievethe credit image data in a variety of ways. For example, the processingmodule 62 may retrieve the credit image data from the memory 70, whichstores the credit image data and may further store a plurality of creditimage data. If the memory 70 is storing a plurality of credit imagedata, then the processing module 62 may retrieve one of a plurality ofcredit image data based on the type to provide the credit card image orin accordance with a retrieval scheme (e.g., round robin, random, user'sordering, etc.). Alternatively, or in addition to, the processing module62 may retrieve the credit image data from a financial server via thewireless transceiver 74. As yet another alternative, the processingmodule 62 may retrieve the credit image data from the contactlesspayment module 60.

The method then proceeds to step 94 where the processing module 62 sendsthe credit image data to the display module 64. The display module 64processes the credit image data to render on image on the display 66.

FIG. 5 is a diagram of another example of credit image data thatincludes the master image layer 80, the design image layer 82, and mayfurther include a transactional image layer 100. The transactional imagelayer 100 includes data relating to the current purchase (e.g., purchaseamount, available balance, etc.) and other relevant data regarding theaccount (e.g., next payment due date, amount due, recent purchases,etc.).

The processing module 62 may receive the transactional image layer 100from the financial institution via the wireless transceiver 74. Forinstance, in response to the request message sent via the wirelesstransceiver, the wireless transceiver receives a radio frequency (RF)signal from a financial institution server, wherein the RF signalincludes the transactional data. The wireless transceiver 74 recoversthe transactional data from the RF signal to produce recoveredtransactional data and provides the recovered transactional data to theprocessing module 62. The processing module 62 generates thetransactional image layer 100 of the credit image data based on therecovered transactional data.

In an embodiment, the processing module 62 may process the master imagelayer 80 and the transactional image layer 100 such that display 66alternates presenting the master image and the transactional image.Alternatively, the processing module 62 may process a request from theuser to display one or the other of the master image and thetransactional image, to jump between the two, or to not display one ormore of the image layers.

FIG. 6 is a logic diagram of another embodiment of a method for creditimage data processing that may be performed by the processing module 62.The method begins at step 110 where the processing module 62 detects theexecuting of the credit payment transaction as previously discussed. Themethod continues at step 112 where the processing module 62 retrievesthe credit image master layer from memory in accordance with thedetecting. For instance, as soon as the processing module detects theexecuting, it begins the retrieval process. Note that the processingmodule 62 may retrieve the master image layer from memory 70, from afinancial institution server via the wireless transceiver 74, and/orfrom the contactless payment module 60.

The method then proceeds to step 114 where the processing module 62retrieves one of the plurality of digital images from memory 70 inaccordance with the detecting. The retrieval may further be done inaccordance with a retrieval scheme. Note that the mobile payment device54-56 may be a cellular telephone with a built-in digital camera suchthat the digital images stored in memory 70 are a collection of picturestaken by an operator of the device 54-56. As part of the retrievalprocess, the processing module 62 may perform an appropriateness checkof the image before providing it to the display module 64.

Such a check begins at step 118 where the processing module 62determines content of the digital image. The method continues at step120 where the processing module 62 analyzes the content of the image todetermine whether it contains inappropriate content. For example, theprocessing module 62 may perform an image recognition algorithm toidentify potentially inappropriate objects within the image. If, at step122, the image does not include inappropriate content, the methodcontinues at step 124 where the processing module retrieves the digitalimage from memory and provides it to the display module 64. If, however,the image potentially includes inappropriate content, the methodproceeds to step 126 where the processing module selections anotherdigital image for appropriateness checking.

The method then proceeds to step 116 where the processing module 62generates credit image data based on the credit image master layer andthe one of the plurality of digital images. The processing module 62 mayfurther process a transactional image layer into the credit image data,wherein the transactional image layer is based on recoveredtransactional data.

FIG. 7 is a schematic block diagram of an embodiment of a contactlesspayment module 60 that includes a key module 130, memory 132, acontactless interface 134, and a memory interface 136. The key module130 contains a unique subscriber identification code and credittransactional information in accordance with a mobile payment protocol.In an embodiment, the unique subscriber identification code may be anInternational Mobile Subscriber Identity (IMSI). The contactlessinterface 134 transmits at least one of the unique subscriberidentification code and the credit transactional information duringexecution of a credit transaction. In an embodiment, the contactlessinterface a radio frequency identification (RFID) interface and/or anear field communication (NFC) interface.

The memory 132, which may be memory as previously defined, stores acredit image data that may be retrieved via the memory interface 136 bythe processing module 62 or other device, module, etc. The credit imagedata includes a master image layer and a design image layer, which maybe a custom design image layer and/or one of a plurality of approveddesign image layers.

FIG. 8 is a schematic block diagram of an embodiment of a financialtransaction apparatus 140, which may be included within, or associatedwith, the payment entity device 12, an issuer device 32-34, and/or anacquirer device 28-30. The apparatus 140 includes a processing module142, memory 144, and an interface 146, which may be a wireless and/or awired interface that enables the apparatus 140 to access the publicnetwork 36. The processing module 142 may be a single processing deviceor a plurality of processing devices. Such a processing device may be amicroprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module 142 may have anassociated memory 144 and/or memory element, which may be a singlememory device, a plurality of memory devices, and/or embedded circuitryof the processing module. Such a memory device may be a read-onlymemory, random access memory, volatile memory, non-volatile memory,static memory, dynamic memory, flash memory, cache memory, and/or anydevice that stores digital information. Note that when the processingmodule 142 implements one or more of its functions via a state machine,analog circuitry, digital circuitry, and/or logic circuitry, the memory144 and/or memory element storing the corresponding operationalinstructions may be embedded within, or external to, the circuitrycomprising the state machine, analog circuitry, digital circuitry,and/or logic circuitry. Further note that, the memory element stores,and the processing module 142 executes, hard coded and/or operationalinstructions corresponding to at least some of the steps and/orfunctions illustrated in FIGS. 9-11.

FIG. 9 is a logic diagram of another embodiment of a method for creditimage data processing that may be processed by the processing module142. The method begins at step 150 where the processing module 142receives, via the interface 146, a digital image from a user via a userdevice 38-42 and/or via a mobile payment device 54-56. The method thenproceeds to step 152 where the processing module 142 determines contentof the digital image. The method continues at step 154 where theprocessing module 142 analyzes the content of the digital image todetermine whether it contains inappropriate content. This may be doneuse image recognition software to identify potentially inappropriateobjects, gestures, etc. within the digital image.

If the digital image does not include inappropriate content, the methodbranches from step 156 to step 158 where the processing module 142generates a design image layer based on the digital image. The methodcontinues at step 160 where the processing module retrieves from memory144 a master image layer. The method continues at step 162 where theprocessing module 142 processes the design image layer and the masterimage layer to produce credit image data. The method continues at step164 where the processing module 142 transmits, via the interface 146,the credit image data.

If the digital image does include inappropriate content, the methodbranches from step 156 to step 166 where the processing module 142rejects the present digital image and begins processing another if oneis available.

FIG. 10 is a logic diagram of another embodiment of a method for creditimage data processing that begins at step 170 where the processingmodule 142 receives, via the interface 146, an indication of execute ofa credit payment transaction by a mobile payment device. The methodcontinues at step 172 where the processing module 142 determinesidentity of a mobile payment device based on the indication. The methodcontinues at step 174 where the processing module 142 generates atransactional data image layer based on at least one of transactionaldata of the mobile payment device and the credit payment transaction.The method continues at step 176 where the processing module 142generates the credit image data based on the design image layer, themaster image layer, and the transactional data image layer. The methodcontinues at step 178 where the processing module 142 transmits, via theinterface 146, the credit image data to the mobile payment device.

FIG. 11 is a logic diagram of another embodiment of a method for creditimage data processing that begins at step 180 where the processingmodule 142 receives, via the interface 146, a request for credit imagedata from a mobile payment device. The method continues at step 182where the processing module 142 retrieves the credit image data based onidentity of mobile payment device. The method continues at step 184where the processing module 142 provides, via the interface 142, thecredit image data to the mobile payment device. The credit image datamay include a master image layer and a design image layer, which may bea custom design image layer and/or one of a plurality of approved designimage layers.

In addition to steps 180-184, the processing module 142 may furtherfunction to: receive, via the interface 146, an indication of execute ofa credit payment transaction from the mobile payment device; generate atransactional data image layer based on at least one of transactionaldata of the mobile payment device and the credit payment transaction;and generate the credit image data based on the design image layer, themaster image layer, and the transactional data image layer.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “coupled to” and/or “coupling” and/or includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for indirect coupling, theintervening item does not modify the information of a signal but mayadjust its current level, voltage level, and/or power level. As mayfurther be used herein, inferred coupling (i.e., where one element iscoupled to another element by inference) includes direct and indirectcoupling between two items in the same manner as “coupled to”. As mayeven further be used herein, the term “operable to” indicates that anitem includes one or more of power connections, input(s), output(s),etc., to perform one or more its corresponding functions and may furtherinclude inferred coupling to one or more other items. As may stillfurther be used herein, the term “associated with”, includes directand/or indirect coupling of separate items and/or one item beingembedded within another item. As may be used herein, the term “comparesfavorably”, indicates that a comparison between two or more items,signals, etc., provides a desired relationship. For example, when thedesired relationship is that signal 1 has a greater magnitude thansignal 2, a favorable comparison may be achieved when the magnitude ofsignal 1 is greater than that of signal 2 or when the magnitude ofsignal 2 is less than that of signal 1.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid offunctional building blocks illustrating the performance of certainsignificant functions. The boundaries of these functional buildingblocks have been arbitrarily defined for convenience of description.Alternate boundaries could be defined as long as the certain significantfunctions are appropriately performed. Similarly, flow diagram blocksmay also have been arbitrarily defined herein to illustrate certainsignificant functionality. To the extent used, the flow diagram blockboundaries and sequence could have been defined otherwise and stillperform the certain significant functionality. Such alternatedefinitions of both functional building blocks and flow diagram blocksand sequences are thus within the scope and spirit of the claimedinvention. One of average skill in the art will also recognize that thefunctional building blocks, and other illustrative blocks, modules andcomponents herein, can be implemented as illustrated or by discretecomponents, application specific integrated circuits, processorsexecuting appropriate software and the like or any combination thereof.

1.-29. (canceled)
 30. A method comprising: receiving, by a first devicefrom a mobile device, transaction data associated with a transaction,wherein the mobile device includes image data, wherein the image data isgenerated by a remote server computer by receiving a retrieval messagefrom the mobile device; retrieving the master image layer and the designimage layer from a memory based on an identifier associated with themobile device, processing the master image layer and the design imagelayer to generate the image data, and transmitting the image data to themobile device; generating, by the first device, an authorization requestmessage to including the transaction data for the transaction; sending,by the first device to a second device, the authorization requestmessage for authorization of the transaction; and receiving, by thefirst device from the second device, an authorization response messageincluding an authorization response for the transaction.
 31. The methodof claim 30, wherein the design image layer is a digital image providedby a user associated with the mobile device.
 32. The method of claim 30,wherein the image data is further generated using a transactional imagelayer, the transactional image layer including at least one oftransactional data associated with the mobile device and transactionaldata for the transaction.
 33. The method of claim 30, wherein the remoteserver computer retrieves the master image layer based on a type of thetransaction, wherein a first type of the transaction is associated witha first master image layer, and wherein a second type of transaction isassociated with a second master image layer.
 34. The method of claim 33,wherein the transaction is a payment transaction.
 35. The method ofclaim 30, wherein the design image layer is generated based on a digitalimage sent from the mobile device to the remote server computer.
 36. Themethod of claim 35, wherein the digital image is sent from the mobiledevice to the remote server computer in the retrieval message.
 37. Themethod of claim 30, wherein the transaction data is received by thefirst device over a communications network.
 38. The method of claim 30,wherein the second device is an issuer device.
 39. A method comprising:detecting, by a processor in a mobile device, an initiation of atransaction using the mobile device; sending, by the processor, aretrieval message for image data to a remote server computer via acommunications network, the retrieval message including an identifierassociated with the mobile device, wherein the remote server computerreceives the retrieval message from the mobile device; retrieves amaster image layer and a design image layer from a memory based on theidentifier associated with the mobile device, processes the master imagelayer and the design image layer to generate image data, and transmitsthe image data to the mobile device; receiving, by the processor, theimage data via the communications network; and displaying, by theprocessor, the image data via a display to enable the mobile device toconduct the transaction.
 40. The method of claim 39, wherein the imagedata is further generated using a transactional image layer, thetransactional image layer including at least one of transactional dataassociated with the mobile device and transactional data for thetransaction.
 41. The method of claim 39, wherein the design image layeris generated based on a digital image sent from the mobile device to theremote server computer.
 42. The method of claim 41, wherein the digitalimage is sent from the mobile device to the remote server computer inthe retrieval message.
 43. The method of claim 39, further comprising:converting, by a wireless transceiver of the mobile device, theretrieval message to an RF signal prior to sending the retrieval messageto the remote server computer.
 44. The method of claim 39, wherein thecommunications network is a wireless communications network.
 45. Amobile device comprising: a processor; and a non-transitorycomputer-readable storage medium, comprising code executable by theprocessor for implementing a method comprising: detecting an initiationof a transaction; sending a retrieval message for image data to a remoteserver computer via a communications network, the retrieval messageincluding an identifier associated with the mobile device, wherein theremote server computer receives the retrieval message from the mobiledevice; retrieves a master image layer and a design image layer from amemory based on the identifier associated with the mobile device,processes the master image layer and the design image layer to generateimage data, and transmits the image data to the mobile device; receivingthe image data via the communications network; and displaying the imagedata via a display to enable the mobile device to conduct thetransaction.
 46. The mobile device of claim 45, wherein the image datais further generated using a transactional image layer, thetransactional image layer including at least one of transactional dataassociated with the mobile device and transactional data for thetransaction.
 47. The mobile device of claim 45, wherein the design imagelayer is generated based on a digital image sent from the mobile deviceto the remote server computer.
 48. The mobile device of claim 47,wherein the digital image is sent from the mobile device to the remoteserver computer in the retrieval message.
 49. The mobile device of claim45, further comprising: converting the retrieval message to an RF signalprior to sending the retrieval message to the remote server computer.